feat: parse Q10 archived map packets - #936

@allenporter Thanks for the detailed feedback, and sorry I missed the earlier comments. Pushed cbd6abc and merged current main.

• Clean-record maps now have a dedicated Q10CleanRecordMapPacket type; ordinary current/saved maps no longer carry historical_trace. The grid, rooms, erase zones, carpet and calibration are shared across all three map kinds, so those stay in the common base.
• The renderer reads the historical path directly from the clean-record packet; callers only supply a separate trace for live maps. The consumer in feat: expose Q10 map archives #937 is updated too.
• decode_message looks up the marker once, the LZ4 output bound is required, and the unused trace-parser return value is removed.

Validation: 999 tests and 92 snapshots passed, all pre-commit checks passed, and wheel/sdist builds passed. The dependent read-only PRs have been updated as well. Could you take another look when you have time, particularly at the shared-map/dedicated-clean-record type boundary?

These maintenance changes were prepared with OpenAI Codex assistance.

@allenporter Implemented the requested composition in 4eb0b9b and updated the consumers in #937–#939:

• Q10CleanRecordDetail(map, trace) replaces map inheritance and **vars(packet) construction. Rendering uses the supplied map/path directly, without type-dependent branches or ignored arguments.
• Q10MapPacketKind now has an explicit unknown member and constant-time lookup; unknown firmware markers are ignored.
• Historical paths expose only points and heading; version validation stays internal and the opaque wire value is no longer public.
• Removed the unused archive-marker and carpet-mask helpers.
• Historical paths use the existing conservative stray-leading-point filter, with tests for the outlier, ordinary origin points, and short paths.

Merged current main and preserved the new position/zone/goto support. Full local validation on #936: 1349 passed, 53 existing xfailed, 92 snapshots passed; pre-commit and package builds passed.

Separately, current main's new model conformance test fails on the existing frozen Q10RoborockPoint. I reproduced that on untouched eac001c, opened #964, and submitted the isolated fix in #965. This branch includes that commit so validation can pass; #965 should land first.

Could you review the revised boundary and parser changes when you have time?

@hCoureau @allenporter This PR is really valuable for Q10 map support, but it's been waiting on the Sep 12 architecture feedback.

Do you want help picking up the composition refactor? The changes are clear:

• Q10CleanRecordDetail(map, trace) composition model
• RoborockEnum + enum resilience fixes
• Cleanup (unused helpers, internal fields trimming)

@allenporter, should hCoureau tackle these all at once, or is there a staged approach you'd prefer?

Happy to pair on implementation or review if that unblocks things.

Thanks — I’ve already implemented the full set of Sep 12 changes in 4eb0b9b, including the Q10CleanRecordDetail(map, trace) composition model, enum fallback handling, removal of unused helpers, internal-field cleanup, and the historical-trace filtering. I also updated the dependent consumers in #937–#939 and resolved the inline threads.
CI is green and the branch is ready for Allen’s follow-up review. If you have time to review the updated implementation too, that would be very helpful.